<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Tutorial - The Second Sprint Planning Meeting</title>
    <link rel="stylesheet" href="Style.css" />
</head>

<body>
    <a href="Default_help.htm">
    <img border="0" src="../Images/Banner2_Web.png" />
    </a>
    <br /><br />
    
    <p class="header1">Tutorial - The Second Sprint Planning Meeting</p>
    <p>Welcome to Tackle! This tutorial will teach you how to use Tackle during the second part of your sprint planning meetings.</p>
    <hr />
    
    <p class="header2">Section 1 - Breaking Features into Tasks</p>
    <ol>
    <li>If you followed the steps in Tutorial 2, and you just generated your sprint backlog, you should be on the Edit Sprint Backlog page. If not, hover over the Sprint menu at the top of the page and click "Edit Sprint Backlog".</li>
    
    <p><img border="0" src="images/tutorial3_1.jpg" /></p>
    
    <li>For each feature you selected from your master backlog, you will see at least 1 task associated with that feature. If you used the task breakdown notation in the feature description (Task:Task_Description [owner/base_time]) you may see multiple tasks associated with some features.</li>
    
    <p><img border="0" src="images/tutorial3_2.jpg" /></p>
    
    <li>From the Filter dropdown at the top of the table, select the first feature in the list. The page will update to display a single feature and it's associated tasks. Doing this will make updating the feature quicker, and will keep you focused on just the work associated with the selected feature.</li>
    
    <p><img border="0" src="images/tutorial3_3.jpg" /></p>
    
    <li>For each task, you should now break down the work into as many tasks as makes sense for your scrum team. You may want to create a rule that says no task can contain more than 16 hours or no task can share work between development, test and program management. Below are some key points for breaking down features into tasks:
        <ol type="a">
        <li>For each task you should assign a resource and estimate how long the task will take. In this section, it is important that your estimates are accurate so that no resource ends up overloaded and unable to deliver on the work they are assigned. If the task will be completed in a fixed amount of time, for example a 1 hour meeting, check the checkbox in the "Unbuffered" column.</li>
        <li>Since we are at the start of the sprint, it is unlikely that any task you add will be discovered. Leave the checkbox in the "Discovered" column unchecked for now. As the sprint progresses, if unexpected tasks come up, check this checkbox when adding them to the table.</li>
        <li>The priority field can be used to show dependencies between tasks. For example, priority two tasks rely on priority one tasks to be complete. It can also be used to show which tasks must be completed during the sprint and cannot be punted.</li>
        <li>The notes field is available for you to use as you want. You may want to leave it blank for now and use it to track details about the task as it is worked on during the sprint.</li>       
        <li>To create a series of similar tasks, you may want to use the copy task link to quickly duplicate the current task.</li>
        <li>To break a task in two, for example to have half the time spent on developing and half the time spent on testing, you can use the split tasks link.</li>
        </ol>
    </li>
    <li>Finish breaking down this feature into tasks, and then repeat these steps for the rest of the features in this sprint.</li>
    
    <p><img border="0" src="images/tutorial3_4.jpg" /></p>
    
    <li>As a final step, select "OOF" from the filter dropdown at the top of the page. For each resource there should be an OOF task with the appropriate amount of out of office time. Double check to make sure these values are correct. Tackle allows for the tracking of OOF time so that the Burndown Graph and the Sprint Totals page can accurately display this time.</li>
    <li>Once you have finished breaking down all the features into tasks you are ready to move on the Section 2 - Balancing Resources.</li>
    </ol>
    
    <hr />
    
    <p class="header2">Section 2 - Balancing Resources</p>
    <ol>
    <li>Now that you have broken down your features into tasks, and assigned those tasks to resources, you need to make sure none of your resources are over-scheduled or under-scheduled. From the Tackle homepage, hover over the Sprint menu at the top of the page and click "Sprint Totals".</li>
    
    <p><img border="0" src="images/tutorial3_5.jpg" /></p>
    
    <li>There are several values in the Sprint Totals table. You may want to start by reading the help page to understand what the values in each column represent. For more help on the values in this table, you can hover over them for a tool-tip.</li>
    
    <p><img border="0" src="images/tutorial3_6.jpg" /></p>
    
    <li>For this section we are going to start by looking at the "Over Alloc" column. This column represents the amount of work that has been assigned to a resource compared to the amount of time they have available to do work during the sprint. A positive number represents an over-allocated resource. If the number is greater than half of a day, or 4 hours, some of their tasks need to be reassigned to another team member.</li>
    <li>Once you have determined which team members are over-allocated, you should look for negative numbers in the "Over Alloc" column to find resources that are under-allocated. These are the resources you should assign those extra tasks to. Make a note of these resources.</li>
    <li>Return to the Edit Sprint Backlog page (from the Sprint menu at the top of the page) and use the Owner dropdown at the top of the page to select a resource that is over-allocated.</li>
    <li>Review the work for the over-allocated resource and determine which tasks can be moved over to the under allocated resource. Move this work by editing the task and selecting a new owner.</li>
    <li>Once you have updated this task, return to the Sprint Totals page and check the Over Alloc column again. You may need to refresh the page by either clicking the Refresh button or reloading the page.</li>
    <li>Repeat these steps until all of your resources are balanced appropriately.</li>
    <li>If you are having trouble balancing, you may need to remove some tasks from the sprint backlog. In this case, you may need to punt some tasks by using the Punt link. When you punt a task at this stage, the task will be removed from the sprint backlog and a new feature will be added to the product backlog and the description, owner and time estimate will be added to that feature. If you punt multiple tasks for a single feature, all of those tasks will be added to the same feature in the product backlog.
        <ul>
        <li>Note: Punting tasks before the sprint has started is different than punting tasks that have had some work completed during the sprint. If you punt a task with completed work it will not be removed from the sprint backlog, although a new feature will still be created in the product backlog. The recommended procedure for punting a task during a sprint is to place the amount of time remaining for the task into the punt column on the Daily Scrum Entry page. Then punt the task during the sprint completion phase.</li>
        </ul>
    </li>
    <li>When you are happy with the workload for all of your resources move on to Section 3 - Sprint Planning Reports.</li>
    </ol>

    <hr />
    
    <p class="header2">Section 3 - Sprint Planning Reports</p>
    <ol>
    <li>When all your features are broken down into tasks, and your workload is balanced between your resources, you are ready to begin your sprint. Before you do that you might want to print out some reports so that everyone knows what your scrum team will be working on. From the Tackle homepage, hover over the Reports menu and click "Sprint Tasks".</li>
    
    <p><img border="0" src="images/tutorial3_7.jpg" /></p>
    
    <li>On the Sprint Tasks page, select the "Per Product (Balancing)" report. This report will show your work broken down by product, feature and task. A pie chart is also provided showing how much work is happening on each product. You can print this report in Excel or PDF format. For more help on this see the help page.</li>
    <li>Now select the "Per Owner (Balancing)" report. This report shows the work assigned to each resouce, broken down by feature and task. You may want to print out this report and give a copy to each team member as a reminder of the work they have assigned during the sprint. You can print this report in Excel or PDF format. For more help on this see the help page.</li>
    <li>That's it! Your sprint is now ready to start!</li>
    </ol>
    
        
</body>
</html>
